Skip to content

feat(release-tracks): add release track preview and version tagging - #903

Open
avwchapman wants to merge 9 commits into
betafrom
790-release-preview-modal
Open

feat(release-tracks): add release track preview and version tagging#903
avwchapman wants to merge 9 commits into
betafrom
790-release-preview-modal

Conversation

@avwchapman

Copy link
Copy Markdown

Adds a release preview modal with summary and object details, validates replacement version bumps, and supports minor or major release tagging.

@avwchapman avwchapman changed the title Add release track preview and version tagging feat(release-tracks): add release track preview and version tagging Jul 28, 2026
@avwchapman
avwchapman requested a review from clemiller July 28, 2026 00:46
@avwchapman avwchapman self-assigned this Jul 28, 2026
@codecov-commenter

codecov-commenter commented Jul 28, 2026

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

❌ Patch coverage is 81.48148% with 65 lines in your changes missing coverage. Please review.
✅ Project coverage is 41.18%. Comparing base (aca11cc) to head (1458dc4).

Files with missing lines Patch % Lines
...release-track-page/release-track-page.component.ts 79.13% 22 Missing and 7 partials ⚠️
...preview-dialog/release-preview-dialog.component.ts 90.25% 16 Missing and 3 partials ⚠️
...ices/connectors/rest-api/release-tracks.service.ts 0.00% 9 Missing ⚠️
...p/components/stix/stix-list/stix-list.component.ts 0.00% 4 Missing ⚠️
...x/relationship-view/relationship-view.component.ts 0.00% 3 Missing ⚠️
.../connectors/rest-api/rest-api-connector.service.ts 0.00% 1 Missing ⚠️
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             beta     #903      +/-   ##
==========================================
+ Coverage   40.66%   41.18%   +0.51%     
==========================================
  Files         199      200       +1     
  Lines       25471    25683     +212     
  Branches     1278     1337      +59     
==========================================
+ Hits        10359    10577     +218     
+ Misses      15067    15057      -10     
- Partials       45       49       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment thread src/app/components/release-preview-dialog/release-preview-dialog.component.ts Outdated
Comment on lines +221 to +225
*ngIf="hasInvalidVersionBumps"
class="release-blocked-message"
role="alert">
<mat-icon aria-hidden="true">warning_amber</mat-icon>
<span> Release is blocked by invalid incoming version bumps. </span>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small wording tweak: this always mentions the release is blocked by invalid version bumps, even if it's just blocked by an API promotion conflict (e.g. staged_to_members: abort). Could we keep this message for when there is an invalid version bump (v1.2 -> v1.4), and add a generic conflict message otherwise? Maybe like "Release is blocked by promotion conflicts."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants